Priority access to a priority access channel

ABSTRACT

Techniques for priority access to a priority access channel are described. In at least some embodiments, a portion of the radio spectrum is divided into general access (GA) channels and priority access (PA) channels. Levels of access to the different channels are controlled based upon priority levels of devices attempting to access the channels. For instance, embodiments employ a channel database that tracks available GA channels and PA channels, and notifies various devices of the available channels. The channel database may also track keys for PA channels that enable authentication of devices for priority access to PA channels. In at least some embodiments, tracking available GA channels and PA channels enables underutilized radio channels to be identified for various uses, such as for wireless broadband communication.

RELATED APPLICATION

This application is a divisional of and claims priority to U.S. patentapplication Ser. No. 14/252,460, filed on Apr. 14, 2014 and titled“Priority Access to a Priority Access Channel,” which claims priority toU.S. Provisional Patent Application No. 61/944,447, filed on Feb. 25,2014 and titled “Priority Access to a Priority Access Channel,” theentire disclosures of which are incorporated in their entirety byreference herein.

BACKGROUND

Many devices today utilize some form of wireless radio frequency (RF)data communication. Examples of RF communication include cellularnetworks (e.g., for cell phones), data broadband (e.g., Wi-Fi®),broadcast television, global positioning system (GPS) navigation, and soforth. Typically, different forms of RF communication use differentportions of the radio spectrum. While many portions of the radiospectrum are allocated and/or licensed for particular uses, there remainportions that are underutilized. Underutilized portions of the radiospectrum may be leveraged for various purposes, such as for unlicensedforms of RF communication. Any use of such underutilized portions,however, must avoid interference with existing licensed RFcommunications and must comply with regulatory requirements for RFcommunication.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Techniques for priority access to a priority access channel aredescribed. In at least some embodiments, a portion of the radio spectrumis divided into general access (GA) channels and priority access (PA)channels. Levels of access to the different channels are controlledbased upon priority levels of devices attempting to access the channels.

For instance, embodiments employ a channel database that tracksavailable GA channels and PA channels, and notifies various devices ofthe available channels. The channel database may also track keys for PAchannels that enable authentication of devices for priority access to PAchannels. In at least some embodiments, tracking available GA channelsand PA channels enables underutilized radio channels to be identifiedfor various uses, such as for wireless broadband communication.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ techniques discussed herein in accordancewith one or more embodiments.

FIG. 2 illustrates an example implementation scenario for determiningavailable wireless channels in accordance with one or more embodiments.

FIG. 3 illustrates an example channel table for tracking information fordifferent wireless channels in accordance with one or more embodiments.

FIG. 4 is a flow diagram that describes steps in a method formaintaining a channel database in accordance with one or moreembodiments.

FIG. 5 is a flow diagram that describes steps in a method fordetermining available channels in a region in accordance with one ormore embodiments.

FIG. 6 is a flow diagram that describes steps in a method fordetermining by a client device available channels in a region inaccordance with one or more embodiments.

FIG. 7 is a flow diagram that describes steps in a method for PA deviceaccess to a PA channel in accordance with one or more embodiments.

FIG. 8 is a flow diagram that describes steps in a method forauthenticating a priority access device in accordance with one or moreembodiments.

FIG. 9 is a flow diagram that describes steps in a method for releasinga priority access channel in accordance with one or more embodiments.

FIG. 10 illustrates an example system and computing device as describedwith reference to FIG. 1, which are configured to implement embodimentsof techniques described herein.

DETAILED DESCRIPTION

Overview

Techniques for priority access to a priority access channel aredescribed. In at least some embodiments, a portion of the radio spectrum(e.g., the 3.5 gigahertz band) is divided into general access (GA)channels and priority access (PA) channels. Levels of access to thedifferent channels are controlled based upon priority levels of devicesattempting to access the channels.

For instance, embodiments employ a channel database that tracksavailable GA channels and PA channels, and notifies various devices ofthe available channels. The channel database may also track keys for PAchannels that enable authentication of devices for priority access to PAchannels. In at least some embodiments, tracking available GA channelsand PA channels enables underutilized radio channels to be identifiedfor various uses, such as for wireless broadband communication.

For instance, consider a scenario where a channel database notifies ageneral access (GA) device of available GA channels and PA channels.Generally, a GA device represents a device (e.g., a mobile device) thatis utilized by a typical user for general purposes. Further to thisscenario, the GA device begins transmitting data over a particular PAchannel. While transmitting over the PA channel, the GA device detectsthat a priority access (PA) device is accessing the PA channel.

Generally, a PA device represents a device (e.g., a mobile device) thatis utilized by a priority user for priority purposes. Examples of PAdevices include devices used for emergency purposes, such as byemergency medical personnel, firefighters, law enforcement officials,and so forth.

Continuing with the scenario, the GA device attempts to authenticate thePA device as being entitled to priority access to the PA channel. The GAdevice, for instance, determines whether a digital signature receivedfrom the PA device matches a digital signature for the PA channel. Ifthe signatures match, the GA device determines that the PA device isentitled to priority access to the PA channel. The GA device may thenrelease the PA channel, e.g., discontinue using the PA channel.Otherwise, if the signatures do not match, the GA device may determinethat the PA device is not authenticated, and thus may continue using thePA channel.

In at least some embodiments, available GA channels and PA channels canbe leveraged to transmit wireless broadband data, such as for datatransmission as part of a wireless local area network (WLAN). The datatransmission, for example, can be performed according to the 802.11Standards for wireless data communication managed by the Institute ofElectrical and Electronics Engineers (IEEE). The 802.11 Standards areoften referred to as “Wi-Fi®”, but are referenced herein in variousways.

In the following discussion, an example environment is first describedthat is operable to employ techniques described herein. Next, a sectionentitled “Example Implementation Scenarios” describes someimplementation scenarios involving techniques discussed herein which maybe employed in the example environment as well as in other environments.Following this, a section entitled “Example Procedures” describes someexample procedures for priority access to a priority access channel inaccordance with one or more embodiments. Finally, a section entitled“Example System and Device” describes an example system and device thatare operable to employ techniques discussed herein in accordance withone or more embodiments.

Example Environment

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ techniques for priority accessto a priority access channel. Environment 100 includes a client device102 which can be embodied as any suitable device such as, by way ofexample and not limitation, a smartphone, a tablet computer, a portablecomputer (e.g., a laptop), a desktop computer, and so forth. One of avariety of different examples of a client device 102 is shown anddescribed below in FIG. 10.

The client device 102 of FIG. 1 is illustrated as including a clientwireless module 104, which is representative of functionality to enablethe client device 102 to communicate wirelessly with other devicesand/or entities. The client wireless module 104 can be configured toenable data communication via a variety of different wireless techniquesand protocols. Examples of such techniques and/or protocols includecellular communications (e.g. 3G, 4G, Long Term Evolution (LTE), and soforth), near field communication (NFC), short-range wireless connections(e.g., Bluetooth), local area wireless networks (e.g., one or morestandards in compliance with IEEE 802.11), wide area wireless networks(e.g., one or more standard in compliance with IEEE 802.16 or 802.22),wireless telephone networks, and so on. For instance, the clientwireless module 104 is configured to perform various aspects oftechniques for priority access to a priority access channel discussedherein.

The client device 102 further includes client wireless hardware 106,which is representative of various hardware components that can beemployed to enable the client device 102 to communicate wirelessly.Examples of the client wireless hardware 106 include radio transmitters,radio receivers, various types and/or combinations of antennas,impedance matching functionality, and so on. In at least someembodiments, the client device 102 is a multi-radio device that cancommunicate via different wireless technologies and/or protocols.

Further included as part of the client device 102 are one or more devicedrivers 108, which are representative of functionality to enable theclient device 102 to interact with various devices, and vice-versa. Forinstance, the device drivers 108 can enable interaction between variousfunctionalities of the client device 102 (e.g., an operating system,applications, services, and so on) and different devices of the clientdevice 102, such as input/output (I/O) devices. The device drivers 108,for instance, can enable interaction between the client wireless module104 and the client wireless hardware 106 to enable the client device 102to transmit and receive wireless signals.

In at least some embodiments, the client device 102 is configured tocommunicate with other devices and/or entities via a communicationapplication 110. Generally, the communication application 110 isrepresentative of functionality to enable different forms ofcommunication via the client device 102. Examples of the communicationapplication 110 include a voice communication application (e.g., a Voiceover Internet Protocol (VoIP) client), a video communicationapplication, a messaging application, a content sharing application, andcombinations thereof. The communication application 110, for instance,enables different communication modalities to be combined to providediverse communication scenarios.

The environment 100 further includes a wireless base station 112, whichis representative of a radio receiver and transmitter that serves as ahub for at least some wireless portions of network(s) 114. In at leastsome embodiments, the wireless base station 112 may serve as a gatewaybetween wired and wireless portions of the network(s) 114. The wirelessbase station 112 also includes functionality for performing variousaspects of the techniques for priority access to a priority accesschannel discussed herein, which are discussed in detail below. Accordingto one or more embodiments, the wireless base station 112 includesfunctionality for wireless communication via a variety of differentwireless technologies and protocols, examples of which are discussedelsewhere herein.

Generally, the network 114 is representative of a single network or acombination of different interconnected networks. In at least someembodiments, the network 114 represents different portions of the radiospectrum that may be leveraged for wireless communication. The network114, for instance, represents radio spectrum in different frequencybands, such as ultra-high frequency (UHF), super-high frequency (SHF),and so forth. The network 114 may also represent a combination ofwireless and wired networks and may be configured in a variety of ways,such as a wide area network (WAN), a local area network (LAN), theInternet, and so forth.

The environment 100 further includes a channel database service 116,which is representative of functionality to track and/or manage variousattributes of wireless channels. The channel database service 116, forinstance, can track channel utilization for different wireless channels,e.g., whether a particular wireless channel is in use and/or isavailable to be used for wireless communication, level of channel usagefor different channels, and so forth. The channel database service 116may track and monitor various other attributes of wireless channel, suchas channel quality, signal-to-noise ratios for different channels, noisefloor in particular channels, and so forth. For example, the channeldatabase service 116 maintains a channel database 118 that stores statusinformation for different wireless channels. As further detailed below,the channel database service 116 may provide channel information fromthe channel database 118 to different entities (e.g., the wireless basestation 112 and/or the client device 102) to enable wireless channels tobe selected for wireless communication.

Further included are channel owners 120, which are representative ofdifferent entities that have certain rights and/or privileges todifferent portions of the radio spectrum. For instance, the channelowners 120 may represent licensees of certain portions of the radiospectrum in a particular market and/or markets, such as televisionnetworks, cellular carriers, radio stations, and so forth. The channelowners 120 may also represent entities that are granted exclusive orshared access to particular frequency bands, such as governmentorganizations, emergency services, academic and/or research entities,and so forth. Generally, licenses and privileges for access to differentportions of the radio spectrum are regulated by governmentorganizations, such as the Federal Communications Commission (FCC) inthe United States, the Office of Communications (OFCOM) in the UnitedKingdom, and so forth. In at least some embodiments, the channel owners120 are considered “incumbents” for respective channels that areentitled to highest priority access to particular channels.

As further illustrated in the environment 100, the wireless base station112 includes an available channel database 122, which is representativeof a database of wireless channels that are available for wirelesscommunication in the network 114. The available channel database 122,for instance, can be populated with channel information received fromthe channel database service 116. In at least some embodiments,available channel information from the available channel database 122can be propagated to the client device 102 to enable a channel and/orchannels to be selected for wireless communication. Further detailsconcerning identification and selection of wireless channels arepresented below.

The environment 100 further includes priority access (PA) devices 124,which are representative of devices that may be granted priority accessto certain channels for wireless communication. The PA devices 124, forinstance, may be devices that are utilized by mission criticalpersonnel, such as emergency medical personnel, firefighters, lawenforcement, and so forth. In at least some embodiments, for instance,the PA devices are not natively allocated channels in a particularregion of the radio spectrum (e.g., are not channel owners 120), but maybe entitled to priority access to such channels according to techniquesdiscussed herein.

The PA devices 124 maintain and/or have access to private keys 126,which are utilized as part of various authentication procedures forauthenticating the PA devices 124 for priority access to wirelesschannels. Further details concerning use of the private keys 126 arediscussed below.

According to implementations discussed herein, techniques can beemployed to establish wireless data communication between the clientdevice 102 and other devices utilizing a variety of different wirelessdata communication techniques and/or protocols. For instance, channelsthat are identified in the available channel database 122 may beleveraged for wireless communication via various of the 802.11standards. This is not intended to be limiting, however, and a widevariety of different wireless techniques and protocols may be utilizedin accordance with the disclosed embodiments. Further, while certainaspects of established wireless protocols (e.g., 802.11, Wi-Fi Direct™,and so on) may be utilized in tandem with techniques discussed herein toenable wireless data communication between devices, techniques discussedherein are inventive and are not to be considered part of theseprotocols as they currently exist.

Having described an example environment in which the techniquesdescribed herein may operate, consider now a discussion of some exampleimplementation scenarios in accordance with one or more embodiments.

Example Implementation Scenarios

The following discussion describes example implementation scenarios forpriority access to a priority access channel in accordance with one ormore embodiments. In portions of the following discussion, referencewill be made to the environment 100 of FIG. 1.

FIG. 2 illustrates an example implementation scenario 200 fordetermining available wireless channels in accordance with one or moreembodiments.

The scenario 200 includes a spectrum portion 202 of the radio spectrum.Generally, the spectrum portion 202 represents a discrete band of radiofrequencies. For instance, the spectrum portion 202 may representfrequencies in the 3.5 gigahertz (GHz) band, e.g., 3550-3650 megahertz.The 3.5 GHz band is presented for purpose of example only, and it is tobe appreciated that the spectrum portion 202 may represent any suitableregion of the radio spectrum.

Further to the scenario 200, the spectrum portion 202 is divided intogeneral access (GA) channels 204 and priority access (PA) channels 206.According to various embodiments, the GA channels 204 can be used bygeneral access devices (e.g., the client device 102) for wireless datatransmission. While channels from the PA channels 206 may also beutilized by general access devices, such use is subject to certainconditions and constraints, examples of which are detailed below.

In the scenario 200, the channel database service 116 determines thatthe GA channels 204 include available general access (GA) channels 208,and the PA channels 206 include available priority access (PA) channels210. Channel availability may be determined in a variety of ways. Forinstance, the channel database service 116 may scan the spectrum portion202 for channels that are not being used for signal transmission by achannel owner 120. Since the channel owners 120 are typically consideredhighest priority users, a channel in use by a channel owner 120 will beconsidered unavailable. As another example, a channel owner 120 or otherentity may notify the channel database service 116 that a channel isavailable.

As yet another example, the channel database service 116 may query thechannel owners 120 as to whether their respective channels are beingutilized. Channel availability may be determined in a variety of otherways not expressly discussed herein.

In at least some embodiments, the available GA channels 208 and theavailable PA channels 210 represent channels that are allocated for useby the channel owners 120, but that are not currently being used.

Further to the scenario 200, the channel database service 116 storeschannel identifiers 212 for the available GA channels 208 and theavailable PA channels 210 as part of the channel database 118. Thechannel database service 116 then provides the channel identifiers 212to the wireless base station 112 to be stored as part of the availablechannel database 122, such as in response to a query from the wirelessbase station 112 for available channels. The channel identifiers 212 mayidentify the available GA channels 208 and the available PA channels 210in various ways, such as with reference to frequency ranges for theindividual channels, channel numbers for the channels (e.g., assignedbased on a regional band plan), and so forth.

In at least some embodiments, the wireless base station 112 can querythe channel database service 116 for available channels periodically,such as every 24 hours, every 12 hours, every hour, and so forth.Alternatively or additionally, the wireless base station 112 can querythe channel database service 116 for available channels in response toan event, such as a shortage of available channels in the availablechannel database 122, increased channel congestion in a geographicalregion, a query from the client device 102 for available channels, andso forth.

Further to the scenario 200, the client device 102 (e.g., via the clientwireless module 104) queries the wireless base station 112 for availablechannels on a periodic basis (e.g., every 24 hours) and/or in responseto various events, such as an initiation of a communication session viathe communication application 110. In response to the query, the clientdevice 102 receives channel identifiers for the available GA channels208 and the available PA channels 210 from the available channeldatabase 122. The client device 102 stores the channel identifiers aspart of a channel set 214, which generally corresponds to channels thatare available to the client device 102 for wireless communication. Theclient device 102 may utilize one or more channels identified in thechannel set 214 to initiate and/or participate in wireless datacommunication.

FIG. 3 illustrates an example channel table 300 for tracking informationfor different wireless channels in accordance with one or moreembodiments. The channel table 300, for instance, tracks channelinformation for channels included in the spectrum portion 202(introduced above), and may track channel information for other channelsas well. In FIG. 3 the channel table 300 is illustrated as beingmaintained as part of the channel identifiers 212 of the channeldatabase 116. The channel table 300, however, may be maintained and/orpropagated to a variety of other entities as well. For instance, thechannel table 300 may be provided in whole or in part to the availablechannel database 122 of the wireless base station 112, and/or to thechannel set 214 maintained by the client device 102.

The channel table 300 includes a channel column 302, a key column 304,and a service identifier (ID) column 306. According to variousembodiments, the channel column 302 tracks identifiers for differentavailable channels. As mentioned above, channel identifiers can bespecified in various ways.

The key column 304 tracks keys for the different available channels. Inat least some embodiments, keys specified in the key column 304represent public keys that are associated with respective availablechannels. As further detailed below, a key for a respective channel canbe used to verify an identity of a PA device that is attempting toaccess a PA channel.

According to one or more embodiments, keys can be used to specifydifferent priority levels for PA devices. For instance, individual keysmay be associated with different priority levels to enable PA devices tobe identified with particular priority levels (e.g., high, medium, low,and so on) based on which keys are linked to the PA devices.

The service ID column 306 tracks service IDs associated with differentchannels. In at least some embodiments, a service ID corresponds to ageneral ID for a particular PA service, such as “emergency medical,”“fire,” “law enforcement,” and so forth. A service ID may alternativelyor additionally identify a particular PA device, such as a media accesscontrol (MAC) address for a device, a mobile equipment ID (MEID) for adevice, a phone number for a device, a subscriber identity module (SIM)ID for a device, and so forth. As yet another example, a service ID maycorrespond to an arbitrarily generated ID for a device and/or class ofdevices.

According to one or more embodiments, service IDs can be used to specifydifferent priority levels for PA devices. For instance, differentservice IDs may be associated with different priority levels to enablePA devices to be identified with particular priority levels (e.g., high,medium, low, and so on) based on which service IDs are linked to the PAdevices.

The channel table 300 further includes a priority access (PA) checkcolumn 308 and a release time column 310. The PA check column 308includes time intervals for different PA channels that specify how oftena GA device is to check for PA device access to a particular channel.The release time column 310 includes time intervals that specify a timelimit for a GA device to release a PA channel when PA device access tothe PA channel is detected. Values indicated in the release time column310, for instance, specify a maximum time that a GA device may continueutilizing a PA channel after the GA device has detected a PA device onthe PA channel.

Further to the channel table 300, consider GA channels 312, whichcorrespond to a set of available GA channels. The channel column 302includes identifiers for the different GA channels 312. Notice, however,that null values are specified for the GA channels 312 in the key column304 as well as the other columns. According to various embodiments, GAchannels are not associated with keys and/or other attributes of PAchannels. As further detailed below, a GA channel can be reallocated asa PA channel by linking a key to the GA channel.

Consider further PA channels 314, which correspond to a set of availablePA channels. The channel column 302 includes identifiers for thedifferent PA channels 314. Further, the key column 304 includes keys forthe respective PA channels 314. In at least some embodiments, a keyentry for a particular PA channel may be populated with the actual keydata, e.g., a string of characters that comprise a public key.Alternatively, a key entry for a particular PA channel may include apointer and/or other identifier for a key. Thus, in at least someembodiments, the size of the channel table 300 can be reduced byutilizing pointers to keys instead of storing the actual key values inthe channel table 300.

The service ID column 306 includes service IDs for the individual PAchannels 314, and the PA check column 308 includes check time intervalsfor the individual PA channels 314. For instance, the PA channel C₅₁ hasa check time of 100 milliseconds (ms). Thus, in a scenario where a GAdevice is using C₅₁, the GA device is instructed to check for PA devicetraffic on C₅₁ every 100 ms. In at least some embodiments,higher-priority PA channels may have shorter check times, whereas lowerpriority PA channels may have longer check times.

The release time column 310 includes release times for the individual PAchannels 314. For instance, the PA channel C₅₁ has a release time of 100ms. Thus, in a scenario where a GA device is using C₅₁ and detects a PAdevice on C₅₁, the GA device has 100 ms to release C₅₁, e.g., toterminate using C₅₁ for wireless data transmission. In at least someembodiments, higher-priority PA channels may have shorter release times,whereas lower priority PA channels may have longer release times.Generally, a release time provides time for a GA device to locate areplacement channel before releasing a PA channel.

Although the channel table 300 illustrates different PA channels withdifferent PA check times, some alternative embodiments may utilize astandard check time that applies to some or all PA channels.

According to one or more embodiments, a particular PA channel may nothave a specified release time, e.g., in the release time column 310. Insuch a scenario, a GA device may be required to release the PA channelimmediately upon detection of a PA device on the channel. Alternatively,a GA device may be allowed to wait until a replacement channel isidentified before releasing a PA channel to a PA device.

In at least some embodiments, the channel table 300 is configurable andreconfigurable, e.g., dynamically and by various entities. For instance,a regulatory body (e.g., the FCC) or other entity may add additional PAchannels by attaching keys to existing GA channels. Further, PA channelsmay be reallocated as GA channels by removing their keys. Thus, a set ofchannels can be reallocated dynamically to accommodate variousscenarios, such as a shortage of PA channels, a shortage of GA channels,and so forth.

According to one or more embodiments, the channel table 300 isregion-specific, e.g., is associated with a particular geographicaland/or market-based region. The channel database service 116, forinstance, may maintain a variety of different channel tables that eachcorrespond to a different geographical region. Thus, when a clientdevice from a particular geographical region requests availablechannels, the channel database service can provide available channelsfrom a channel table for that particular geographical region.

Having discussed some example implementation scenarios, consider nowsome example procedures in accordance with one or more embodiments.

Example Procedures

FIG. 4 is a flow diagram that describes steps in a method formaintaining a channel database in accordance with one or moreembodiments. The channel database service 116, for instance, may employthe method to maintain the channel database 118.

Step 400 maintains a database of available channels for a region. Oneexample of such a database is the channel database 118 maintained by thechannel database service 116. In at least some embodiments, the channeldatabase 118 tracks available channels for multiple differentgeographical regions, such as different channel tables 300 thatindividually correspond to different geographical regions. Thus,available GA channels and PA channels for different geographical regionscan be tracked.

Step 402 receives a query for available channels in the region. Thechannel database service 116, for example, receives a query from thewireless base station 112 for available channels in the region.

Step 404 provides a notification of available channels in the region.For instance, the channel database service 116 notifies the wirelessbase station 112 and/or the client device 102 of available channels,e.g., the available GA channels 204 and/or the available PA channel 206introduced above. The channel database service 116 may provide variousinformation for the available channels, such as information from thechannel table 300.

Step 406 receives an indication of a change to channel availability. Thechannel database service 116, for instance, may determine that one ormore GA channels and/or PA channels have become available. For example,a channel owner 120 may release a channel, and thus the channel databaseservice may ascertain that the channel is now available.

Alternatively or additionally, the channel database service 116 maydetermine that one or more previously-available GA channels and/or PAchannels are no longer available. For example, a channel owner 120 maybegin using a channel, and thus the channel database service 116 mayascertain that the channel is no longer available.

Step 408 provides a notification of the change to channel availability.For instance, the channel database service 116 notifies the wirelessbase station 112 and/or the client device 102 of the change. The channeldatabase service 116, for example, may update the channel table 300 toadd newly-available channels and/or to delete channels that are nolonger available. Updates to the channel table 300 can be provided to(e.g., pushed to and/or pulled from) the wireless base station 112. Thewireless base station 112 may update the available channel database 122based on the notification, and may further provide such updates to theclient device 102.

FIG. 5 is a flow diagram that describes steps in a method fordetermining available channels in a region in accordance with one ormore embodiments.

Step 500 submits a query for available channels in a region. Thewireless base station 112, for instance, queries the channel databaseservice 116 for available wireless channels in a particular geographicalregion and/or set of geographical regions.

Step 502 receives identifiers and attributes for available channels inthe region. For example, the wireless base station 112 receivesinformation from a channel table (e.g., the channel table 300) from thechannel database service 116. According to one or more embodiments, aportion of the channel table may be received, or a copy of the entirechannel table. The identifiers and attributes may correspond toavailable GA channels and available PA channels. The wireless basestation 112, for instance, stores the identifiers and attributes for theavailable channels as part of the available channel database 122.

Step 504 receives a query from a client device for available channels inthe region. The wireless base station 112, for example, receives a queryfrom the client device 102 for available channels. In at least someembodiments, the query includes geographical position information forthe client device, such as Global Positioning System (GPS) coordinates,a street address, a city or town name, and/or any other suitable way ofdescribing a location of the client device.

Step 506 provides a notification to the client device of the identifiersand attributes for available channels in the region. For instance, thewireless base station 112 provides various information regardingavailable channels from the available channel database 122 to the clientdevice 102. In at least some embodiments, the information includes someor all of a channel table that tracks the available channels in theregion, and includes information for available GA channels and availablePA channels.

According to one or more embodiments, if a change to available channelsis received (e.g., as discussed above), the change can be provided(e.g., pushed) to the client device. For instance, the wireless basestation 112 may receive an update to available channels from the channeldatabase service 116, and may push the update to the client device 102.In at least some embodiments, the update may be pushed independent of aquery from the client device.

FIG. 6 is a flow diagram that describes steps in a method fordetermining by a client device available channels in a region inaccordance with one or more embodiments.

Step 600 submits a query for available channels in a region. The clientdevice 102, for instance, queries the wireless base station 112 foravailable wireless channels in a particular geographical region and/orset of geographical regions. In at least some embodiments, the queryinclude geographical position information for the client device 102,examples of which are discussed above.

Step 602 receives identifiers and attributes for available channels inthe region. For example, the client device 102 receives information froma channel table (e.g., the channel table 300) from the wireless basestation 112. According to one or more embodiments, a portion of thechannel table may be received, or a copy of the entire channel table.The identifiers and attributes may correspond to available GA channelsand available PA channels. The client device 102, for instance, storesthe identifiers and attributes for the available channels as part of thechannel set 214.

According to one or more embodiments, the client device 102 receiveskeys (e.g., public keys) for available PA channels, such as keysspecified in the key column 304 of the channel table 300. The clientdevice 102 may cache the keys locally such that the client device 102need not download a key for a particular PA channel every time theclient device 102 receives an indication that the PA channel isavailable.

In at least some embodiments, the association of a key with a channelindicates that the channel is a PA channel. If a channel has noassociated key, this indicates that the channel is a GA channel. Thus, adevice (e.g., the client device) can differentiate PA channels from GAchannels based on which channels have associated keys and which do not.

Step 604 selects a set of channels from the available channels includinga priority access (PA) channel. For example, the client device 102selects one or more channels for wireless data transmission. The one ormore channels may be selected based on various criteria, such as channelquality, channel congestion, channel proximity to other availablechannels, and so forth. Alternatively or additionally, the set ofchannels may be selected based on use-specific parameters, such asparameters specified by the communication application 110 forcommunication sessions.

Step 606 utilizes the set of channels for wireless data transmission.The client device 102, for instance, initiates and/or participates inwireless data transmission via the set of available channels, includingthe priority access channel. In at least some embodiments, the set ofchannels may include both a GA channel and a PA channel, or may includeonly a PA channel and/or PA channels.

Step 608 detects a priority access (PA) device on the PA channel. Forexample, the client device 102 detects that a PA device 124 is accessingor attempting to access the PA channel. The PA device can be detected invarious ways, such as via a PA device identifier and/or designatortransmitted by the PA device.

In at least some embodiments, the PA device is detected based on a checkthat is performed periodically, e.g., according to a PA check timespecified for the PA channel. Examples of PA check times are discussedabove with reference to channel table 300.

Step 610 ascertains whether the priority access device is authenticated.The client device 102, for instance, verifies whether the PA device isauthenticated as a PA device that is entitled to priority access to thePA channel. An example way of authenticating a PA device is describedbelow.

If the priority access device is authenticated (“Yes”), step 612releases the priority access channel. For instance, the client device102 stops transmitting data over the PA channel. An example way ofreleasing a PA channel is described below. The authenticated PA devicemay then utilize the PA channel without interruption from the GA device.

If the priority access device is not authenticated (“No”), step 614 doesnot release the priority access channel. If the PA device failsauthentication, for example, the client device may continue transmittingdata over the PA channel. In at least some embodiments, a PA device'sfailure to be authenticated may indicate that a device is attempting tospoof a PA device, e.g., a GA device is attempting to imitate a PAdevice to gain priority access to a PA channel.

FIG. 7 is a flow diagram that describes steps in a method for PA deviceaccess to a PA channel in accordance with one or more embodiments.

Step 700 encrypts priority access (PA) device attributes with a priorityaccess key to generate an encrypted package. The PA device 124, forinstance, encrypts various information with its respective private key126. Examples of such information include a device identifier, examplesof which are discussed above. Other examples of such information includea service ID associated with the PA device, such as a service IDspecified in the service ID column 306 of the channel table 300. Avariety of other types of information may additionally or alternativelybe encrypted via a priority access key to generate an encrypted package.Generally, an encrypted package represents an encrypted set ofinformation that can be utilized in various ways, such as forauthenticating a PA device.

As referenced above, in at least some embodiments a priority access keymay represent a private key that is maintained by the PA devices 124 toencrypt data in various scenarios.

Step 702 transmits the encrypted package while accessing a priorityaccess channel. The PA device 124, for instance, can transmit theencrypted package as part of a request for access to a PA channel.Alternatively or additionally, the PA device 124 can transmit theencrypted package while transmitting data over a PA channel, e.g.,during an established communication session between the PA device andanother device.

According to one or more embodiments, a PA device can transmit theencrypted package in various ways. For instance, the encrypted packagecan be transmitted in a packet header of communication data that istransmitted over a PA channel. Other example ways of transmitting anencrypted package include as part of an information element transmittedby a PA device, within a control channel (e.g., in a duplex gap), aspart of an identification beacon transmitted by a PA device, and soforth.

In at least some embodiments, an encrypted package is utilized toauthenticate a PA device. For instance, consider the following exampleprocedure.

FIG. 8 is a flow diagram that describes steps in a method forauthenticating a PA device in accordance with one or more embodiments.

Step 800 receives an encrypted package from a priority access (PA)device that is accessing a priority access (PA) channel. The clientdevice 102, for instance, receives an encrypted package from the PAdevice 124 as part of a request from the PA device 124 to access a PAchannel, and/or while the PA device 124 is transmitting data over the PAchannel.

Step 802 decrypts the encrypted package to expose PA device attributes.The client device 102, for instance, uses a decryption key (e.g., apublic key) specified for the PA channel. With reference to the channeltable 300, for example, a key from the key column 304 that correspondsto the PA channel is retrieved and used to decrypt the encryptedpackage.

Step 804 ascertains whether the PA device attributes match attributesspecified for the PA channel. Examples of such attributes includeattributes specified for the PA channel in service ID column 306 of thechannel table 300. See the discussion of the channel table 300, above,for specific examples of such attributes.

If the PA device attributes match attributes specified for the PAchannel (“Yes”), step 806 authenticates the PA device for priorityaccess to the PA channel. For instance, if the client device 102authenticates the PA device 124, the client device 102 may release thePA channel, e.g., may stop transmitting over the PA channel.

If the PA device attributes do not match attributes specified for the PAchannel (“No”), step 808 fails authentication of the PA device forpriority access to the PA channel.

FIG. 9 is a flow diagram that describes steps in a method for releasinga PA channel in accordance with one or more embodiments.

Step 900 ascertains whether a priority access (PA) channel to bereleased is associated with a release time. Examples of PA channelrelease times are discussed above with reference to the channel table300. In at least some embodiments, different PA channels may beassociated with different release times. Alternatively, a group ofdifferent PA channels may be generally associated with the same releasetime.

If the PA channel is associated with a release time (“Yes”), step 902releases the PA channel when a connection to a new channel isestablished or the release time elapses, whichever occurs first. Forinstance, a release time counter may begin elapsing when a PA device isdetected on a PA channel. While the counter is elapsing, a GA device(e.g., the client device 102) may search for a replacement channel,e.g., an available PA channel and/or an available GA channel. If areplacement channel is located before the counter elapses, the GA devicemay switch to the replacement channel and release the PA channel. If thecounter elapses before a replacement channel is identified, the PAchannel will be released and the GA device may continue looking for areplacement channel.

In an alternative embodiment, a PA channel may be associated with aconditional release, e.g., that is conditioned upon GA device currentlyusing the PA channel finding a replacement channel. In such embodiments,a GA device may look for a replacement channel while continuing to usethe PA channel, and may continue to use the PA channel until areplacement channel is located.

If the PA channel is not associated with a release time (“No”), step 904releases the PA channel and searches for a replacement channel. A GAdevice, for instance, will release the channel immediately upondetection of a PA device on the PA channel. The GA device may look for areplacement channel after releasing the PA channel.

At least some embodiments may employ channel aggregation (e.g., carrieraggregation) such that multiple channels are used together for datatransmission. Such embodiments are particularly useful for transmissionscenarios that require high bandwidth, such as for multimediacommunication sessions. When channel aggregation is employed, multiplePA channels may be utilized, and/or a combination of GA channels and PAchannels.

When a GA device is employing channel aggregation that utilizes a PAchannel and a PA device is detected on the PA channel, instead ofreleasing the PA channel, the GA device may simply reduce transmissionpower over the PA channel (and optionally, other channels as well) toreduce interference with data transmission from the PA device. Thus,embodiments may enable a GA device to continue using a PA channel inchannel aggregation scenarios, even when PA device traffic is detectedon the PA channel.

Having discussed some example procedures, consider now a discussion ofan example system and device in accordance with one or more embodiments.

Example System and Device

FIG. 10 illustrates an example system generally at 1000 that includes anexample computing device 1002 that is representative of one or morecomputing systems and/or devices that may implement various techniquesdescribed herein. For example, the client device 102 discussed abovewith reference to FIG. 1 can be embodied as the computing device 1002.The computing device 1002 may be, for example, a server of a serviceprovider, a device associated with the client (e.g., a client device),an on-chip system, and/or any other suitable computing device orcomputing system.

The example computing device 1002 as illustrated includes a processingsystem 1004, one or more computer-readable media 1006, and one or moreI/O Interfaces 1008 that are communicatively coupled, one to another.Although not shown, the computing device 1002 may further include asystem bus or other data and command transfer system that couples thevarious components, one to another. A system bus can include any one orcombination of different bus structures, such as a memory bus or memorycontroller, a peripheral bus, a universal serial bus, and/or a processoror local bus that utilizes any of a variety of bus architectures. Avariety of other examples are also contemplated, such as control anddata lines.

The processing system 1004 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 1004 is illustrated as including hardware element 1010 that maybe configured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 1010 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable media 1006 is illustrated as includingmemory/storage 1012. The memory/storage 1012 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage 1012 may include volatile media (such as random accessmemory (RAM)) and/or nonvolatile media (such as read only memory (ROM),Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage 1012 may include fixed media (e.g., RAM, ROM, a fixedhard drive, and so on) as well as removable media (e.g., Flash memory, aremovable hard drive, an optical disc, and so forth). Thecomputer-readable media 1006 may be configured in a variety of otherways as further described below.

Input/output interface(s) 1008 are representative of functionality toallow a user to enter commands and information to computing device 1002,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone (e.g., for implementing voice and/or spoken input),a scanner, touch functionality (e.g., capacitive or other sensors thatare configured to detect physical touch), a camera (e.g., which mayemploy visible or non-visible wavelengths such as infrared frequenciesto detect movement that does not involve touch as gestures), and soforth. Examples of output devices include a display device (e.g., amonitor or projector), speakers, a printer, a network card,tactile-response device, and so forth. Thus, the computing device 1002may be configured in a variety of ways as further described below tosupport user interaction.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,” and“component” as used herein generally represent software, firmware,hardware, or a combination thereof. The features of the techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 1002. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent storage of information in contrast to mere signaltransmission, carrier waves, or signals per se. Computer-readablestorage media do not include signals per se. The computer-readablestorage media includes hardware such as volatile and non-volatile,removable and non-removable media and/or storage devices implemented ina method or technology suitable for storage of information such ascomputer readable instructions, data structures, program modules, logicelements/circuits, or other data. Examples of computer-readable storagemedia may include, but are not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, hard disks, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or otherstorage device, tangible media, or article of manufacture suitable tostore the desired information and which may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 1002, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared, and other wireless media.

As previously described, hardware elements 1010 and computer-readablemedia 1006 are representative of instructions, modules, programmabledevice logic and/or fixed device logic implemented in a hardware formthat may be employed in some embodiments to implement at least someaspects of the techniques described herein. Hardware elements mayinclude components of an integrated circuit or on-chip system, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), a complex programmable logic device (CPLD), and otherimplementations in silicon or other hardware devices. In this context, ahardware element may operate as a processing device that performsprogram tasks defined by instructions, modules, and/or logic embodied bythe hardware element as well as a hardware device utilized to storeinstructions for execution, e.g., the computer-readable storage mediadescribed previously.

Combinations of the foregoing may also be employed to implement varioustechniques and modules described herein. Accordingly, software,hardware, or program modules and other program modules may beimplemented as one or more instructions and/or logic embodied on someform of computer-readable storage media and/or by one or more hardwareelements 1010. The computing device 1002 may be configured to implementparticular instructions and/or functions corresponding to the softwareand/or hardware modules. Accordingly, implementation of modulesdiscussed herein as software may be achieved at least partially inhardware, e.g., through use of computer-readable storage media and/orhardware elements 1010 of the processing system. The instructions and/orfunctions may be executable/operable by one or more articles ofmanufacture (for example, one or more computing devices 1002 and/orprocessing systems 1004) to implement techniques, modules, and examplesdescribed herein.

As further illustrated in FIG. 10, the example system 1000 enablesubiquitous environments for a seamless user experience when runningapplications on a personal computer (PC), a television device, and/or amobile device. Services and applications run substantially similar inall three environments for a common user experience when transitioningfrom one device to the next while utilizing an application, playing avideo game, watching a video, and so on.

In the example system 1000, multiple devices are interconnected througha central computing device. The central computing device may be local tothe multiple devices or may be located remotely from the multipledevices. In one embodiment, the central computing device may be a cloudof one or more server computers that are connected to the multipledevices through a network, the Internet, or other data communicationlink.

In one embodiment, this interconnection architecture enablesfunctionality to be delivered across multiple devices to provide acommon and seamless experience to a user of the multiple devices. Eachof the multiple devices may have different physical requirements andcapabilities, and the central computing device uses a platform to enablethe delivery of an experience to the device that is both tailored to thedevice and yet common to all devices. In one embodiment, a class oftarget devices is created and experiences are tailored to the genericclass of devices. A class of devices may be defined by physicalfeatures, types of usage, or other common characteristics of thedevices.

In various implementations, the computing device 1002 may assume avariety of different configurations, such as for computer 1014, mobile1016, and television 1018 uses. Each of these configurations includesdevices that may have generally different constructs and capabilities,and thus the computing device 1002 may be configured according to one ormore of the different device classes. For instance, the computing device1002 may be implemented as the computer 1014 class of a device thatincludes a personal computer, desktop computer, a multi-screen computer,laptop computer, netbook, and so on.

The computing device 1002 may also be implemented as the mobile 1016class of device that includes mobile devices, such as a mobile phone,portable music player, portable gaming device, a tablet computer, amulti-screen computer, and so on. The computing device 1002 may also beimplemented as the television 1018 class of device that includes deviceshaving or connected to generally larger screens in casual viewingenvironments. These devices include televisions, set-top boxes, gamingconsoles, and so on.

The techniques described herein may be supported by these variousconfigurations of the computing device 1002 and are not limited to thespecific examples of the techniques described herein. For example,functionalities discussed with reference to the client device 102, thewireless base station 112, and/or the channel database service 116 maybe implemented all or in part through use of a distributed system, suchas over a “cloud” 1020 via a platform 1022 as described below.

The cloud 1020 includes and/or is representative of a platform 1022 forresources 1024. The platform 1022 abstracts underlying functionality ofhardware (e.g., servers) and software resources of the cloud 1020. Theresources 1024 may include applications and/or data that can be utilizedwhile computer processing is executed on servers that are remote fromthe computing device 1002. Resources 1024 can also include servicesprovided over the Internet and/or through a subscriber network, such asa cellular or Wi-Fi™ network.

The platform 1022 may abstract resources and functions to connect thecomputing device 1002 with other computing devices. The platform 1022may also serve to abstract scaling of resources to provide acorresponding level of scale to encountered demand for the resources1024 that are implemented via the platform 1022. Accordingly, in aninterconnected device embodiment, implementation of functionalitydescribed herein may be distributed throughout the system 1000. Forexample, the functionality may be implemented in part on the computingdevice 1002 as well as via the platform 1022 that abstracts thefunctionality of the cloud 1020.

Discussed herein are a number of methods that may be implemented toperform techniques discussed herein. Aspects of the methods may beimplemented in hardware, firmware, or software, or a combinationthereof. The methods are shown as a set of blocks that specifyoperations performed by one or more devices and are not necessarilylimited to the orders shown for performing the operations by therespective blocks. Further, an operation shown with respect to aparticular method may be combined and/or interchanged with an operationof a different method in accordance with one or more implementations.Aspects of the methods can be implemented via interaction betweenvarious entities discussed above with reference to the environment 100.

CONCLUSION

Techniques for priority access to a priority access channel aredescribed. Although embodiments are described in language specific tostructural features and/or methodological acts, it is to be understoodthat the embodiments defined in the appended claims are not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as example forms of implementing theclaimed embodiments.

What is claimed is:
 1. A system comprising: one or more processors; andone or more computer-readable storage media having instructions storedthereon that, responsive to execution by the one or more processors,cause the one or more processors to perform operations including:receiving, from a channel database service, a portion of an availablechannel database, the portion of the available channel databaseincluding entries for priority access channels and general accesschannels in a region covered by the system, wherein the entries for thepriority access channels include different keys for different priorityaccess channels, wherein each of the keys corresponds to a respectivepriority level for a respective priority access device of a plurality ofpriority access devices; receiving a query, from one general accessdevice of a plurality of general access devices served by the system,the received query being for available wireless channels in the region;providing a notification of available wireless channels in the region tothe general access device, the notification including an identifier forat least one of the priority access channels and a respective key thatis usable to authenticate a priority access device of the plurality ofpriority access devices for priority access to the priority accesschannel; receiving an indication of a change of channel availability inthe region; and providing a notification of the change in channelavailability to at least one general access device of the plurality ofgeneral access devices and to the channel database service.
 2. A systemas recited in claim 1, wherein the query includes geographical positioninformation for the region.
 3. A system as recited in claim 1, whereinthe system comprises a wireless base station in the region.
 4. A systemas recited in claim 1, wherein the notification of available wirelesschannels includes a priority access check time for the priority accesschannel that specifies how frequently the general access device that isutilizing the priority access channel is to check for priority accessdevice access to the priority access channel.
 5. A system as recited inclaim 1, wherein the notification of available wireless channelsincludes a release time for the priority access channel that specifies amaximum time that the general access device may continue utilizing thepriority access channel after the general access device has detected thepriority access device on the priority access channel.
 6. A system asrecited in claim 1, wherein at least some of the keys in the availablechannel database correspond to different priority levels for therespective priority access devices.
 7. A system as recited in claim 1,wherein the operations further comprise: receiving an indication of afurther change of channel availability in the region; and providing anotification of the further change in channel availability to the atleast one general access device of the plurality of general accessdevices.
 8. A method comprising: receiving, from a channel databaseservice, a portion of an available channel database, the portion of theavailable channel database including entries for priority accesschannels and general access channels in a region covered by a system,wherein the entries for the priority access channels include differentkeys for different priority access channels, wherein each of the keyscorresponds to a respective priority level for a respective priorityaccess device of a plurality of priority access devices; receiving aquery for available wireless channels in the region; and providing, by aprocessing system, a notification of available wireless channels in theregion including an identifier for at least one of the priority accesschannels and a respective key that is usable to authenticate a priorityaccess device of the plurality of priority access devices for priorityaccess to the priority access channel; receiving an indication of achange of channel availability in the region; and providing anotification of the change in channel availability to at least onegeneral access device of a plurality of general access devices and tothe channel database service.
 9. A method as recited in claim 8, whereinthe query includes geographical position information for the region. 10.A method as recited in claim 8, wherein the query is from a generalaccess client device of the plurality of general access devices.
 11. Amethod as recited in claim 8, wherein the notification of availablewireless channels includes a priority access check time for the priorityaccess channel that specifies how frequently a general access device ofthe plurality of general access devices that is utilizing the priorityaccess channel is to check for priority access device access to thepriority access channel.
 12. A method as recited in claim 8, wherein thenotification of available wireless channels includes a release time forthe priority access channel that specifies a maximum time that a generalaccess device of the plurality of general access devices may continueutilizing the priority access channel after the general access devicehas detected the priority access device on the priority access channel.13. A method as recited in claim 8, wherein at least some of the keys inthe available channel database correspond to different priority levelsfor the respective priority access devices.
 14. A method as recited inclaim 8, further comprising: receiving an indication of a further changeof channel availability in the region, and providing a notification ofthe further change in channel availability to the at least one generalaccess device of the plurality of general access devices.
 15. A methodcomprising: receiving, from a channel database service, a portion of anavailable channel database, the portion of the available channeldatabase including entries for priority access channels and generalaccess channels in a region covered by a system, wherein the entries forthe priority access channels include different keys for differentpriority access channels, wherein each of the keys corresponds to arespective priority level for a respective priority access device of aplurality of priority access devices; receiving, from a general accessclient device, a query for available wireless channels in the region;and providing, by a processing system, a notification to the generalaccess client device of available wireless channels in the regionincluding an identifier for at least one of the priority access channelsand at least one key of the different keys for the at least one priorityaccess channel, wherein the at least one key is usable by the generalaccess client device to authenticate the respective priority accessdevice for priority access to the priority access channel; receiving anindication of a change of channel availability in the region; andproviding a notification of the change in channel availability to thegeneral access client device and to the channel database service.
 16. Amethod as recited in claim 15, wherein the notification of availablewireless channels includes a priority access check time for the priorityaccess channel that specifies how frequently the general access clientdevice that is utilizing the priority access channel is to check forpriority access device access to the priority access channel.
 17. Amethod as recited in claim 15, wherein the notification of availablewireless channels includes a release time for the priority accesschannel that specifies a maximum time that the general access clientdevice may continue utilizing the priority access channel after thegeneral access client device has detected the priority access device onthe priority access channel.
 18. A method as recited in claim 15,further comprising: receiving a further indication of a further changeof channel availability in the region, the indication indicating one ormore of that a new channel is available in the region, or that apreviously-available channel is no longer available; and providing anotification of the further change in channel availability to thegeneral access client device.